Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 470ae9bda954d38748beaad2b67ec6a6adebfd88669f894256c2b39157ec640a

Tx prefix hash: 5c3a8e446c9ecb6a06c89022d4cc8decfb753c401b06dcae2ab38cf87c48be1b
Tx public key: 9116f1e8418c94f52a77c5051bc9c67a05f365dc34e45887052c8c8132a9c906
Timestamp: 1747386867 Timestamp [UCT]: 2025-05-16 09:14:27 Age [y:d:h:m:s]: 00:182:15:42:16
Block: 1284065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128252 RingCT/type: yes/0
Extra: 019116f1e8418c94f52a77c5051bc9c67a05f365dc34e45887052c8c8132a9c9060211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d9816ef081c916d4430147ebcfe485ad1e3dd992b551b16b77e339f861d20d9 0.600000000000 1771500 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": 1284075, "vin": [ { "gen": { "height": 1284065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d9816ef081c916d4430147ebcfe485ad1e3dd992b551b16b77e339f861d20d9" } } ], "extra": [ 1, 145, 22, 241, 232, 65, 140, 148, 245, 42, 119, 197, 5, 27, 201, 198, 122, 5, 243, 101, 220, 52, 228, 88, 135, 5, 44, 140, 129, 50, 169, 201, 6, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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