Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ff569497cc223f2ec25d3acc50d03990b3bbf74e1962ee4bfaa5e56df0b195e5

Tx prefix hash: 51b6c865c782132e0a497482f78edcb747075ed1efc628426f544f15f62e7f16
Tx public key: a576653b82809d4e581c3e81205ab90dc9963a0f39d56f05280efe1c1f94dca1
Timestamp: 1747577647 Timestamp [UCT]: 2025-05-18 14:14:07 Age [y:d:h:m:s]: 00:143:05:44:22
Block: 1285650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100016 RingCT/type: yes/0
Extra: 01a576653b82809d4e581c3e81205ab90dc9963a0f39d56f05280efe1c1f94dca10211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33cee16cf0c9a5e11d86be5e91aeb0a36427c2f40d973a0b536012daa1a39625 0.600000000000 1773115 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1285660, "vin": [ { "gen": { "height": 1285650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33cee16cf0c9a5e11d86be5e91aeb0a36427c2f40d973a0b536012daa1a39625" } } ], "extra": [ 1, 165, 118, 101, 59, 130, 128, 157, 78, 88, 28, 62, 129, 32, 90, 185, 13, 201, 150, 58, 15, 57, 213, 111, 5, 40, 14, 254, 28, 31, 148, 220, 161, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8