Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c33536a7dab4a22a21364d1d7224f6887db401239eabf714230cc69ae6bb942

Tx prefix hash: 54e1ddc132aad260263591428e4e16256f6a684fb7fa8e44d6b53e64d5644e39
Tx public key: f403b8448751f4f304aeef17ac72b69822fe8ddd0a2a97fb427c7af71cc717be
Timestamp: 1754529140 Timestamp [UCT]: 2025-08-07 01:12:20 Age [y:d:h:m:s]: 00:073:18:03:48
Block: 1341829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51719 RingCT/type: yes/0
Extra: 01f403b8448751f4f304aeef17ac72b69822fe8ddd0a2a97fb427c7af71cc717be0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 356c1aa510d6b5d9cc51ff215c85a179c68dd1dc9a317deb47dbebfe6cf56df9 0.600000000000 1829656 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": 1341839, "vin": [ { "gen": { "height": 1341829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "356c1aa510d6b5d9cc51ff215c85a179c68dd1dc9a317deb47dbebfe6cf56df9" } } ], "extra": [ 1, 244, 3, 184, 68, 135, 81, 244, 243, 4, 174, 239, 23, 172, 114, 182, 152, 34, 254, 141, 221, 10, 42, 151, 251, 66, 124, 122, 247, 28, 199, 23, 190, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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