Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60418645b011a60896d7e68cb8da5f1efdb9340c1693b74b083b06935fac4ac4

Tx prefix hash: 04b4a2dec27083753847add0cc1f76188b7bbb86e899cd515c4dbf08c66309c2
Tx public key: fb2262b7cdbf80d06f16fad9ce1f30b9574c82d4db890d424db72fb27787ae05
Timestamp: 1735953691 Timestamp [UCT]: 2025-01-04 01:21:31 Age [y:d:h:m:s]: 00:306:00:29:22
Block: 1189689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216192 RingCT/type: yes/0
Extra: 01fb2262b7cdbf80d06f16fad9ce1f30b9574c82d4db890d424db72fb27787ae05021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26ae36bf907eb854213c2dd95d84f72daae4e76fb776273ae9264e9ada6e730f 0.600000000000 1676200 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": 1189699, "vin": [ { "gen": { "height": 1189689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ae36bf907eb854213c2dd95d84f72daae4e76fb776273ae9264e9ada6e730f" } } ], "extra": [ 1, 251, 34, 98, 183, 205, 191, 128, 208, 111, 22, 250, 217, 206, 31, 48, 185, 87, 76, 130, 212, 219, 137, 13, 66, 77, 183, 47, 178, 119, 135, 174, 5, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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