Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 090cfb7b6bc3c14d13c479f5870702bc840f0722eba3de92d5d787ff9993e5a1

Tx prefix hash: 4cc20cdbed12a96b54ed639cbf256f72d5454e1d9eaa8264da2d5614c6f21184
Tx public key: 32b4ef06dcbe944c7b2526ef3cc60a4052930e544e9ea8ea3bded4837f0d0737
Timestamp: 1749949043 Timestamp [UCT]: 2025-06-15 00:57:23 Age [y:d:h:m:s]: 00:155:13:47:15
Block: 1305206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108952 RingCT/type: yes/0
Extra: 0132b4ef06dcbe944c7b2526ef3cc60a4052930e544e9ea8ea3bded4837f0d073702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472dca75315fa3b3338a016a75a5e18b7f9358cdf37da46925f5225d415577c4 0.600000000000 1792805 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": 1305216, "vin": [ { "gen": { "height": 1305206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472dca75315fa3b3338a016a75a5e18b7f9358cdf37da46925f5225d415577c4" } } ], "extra": [ 1, 50, 180, 239, 6, 220, 190, 148, 76, 123, 37, 38, 239, 60, 198, 10, 64, 82, 147, 14, 84, 78, 158, 168, 234, 59, 222, 212, 131, 127, 13, 7, 55, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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