Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f343c8c81d329edb34da488d7c964c442837d3df67171be107a537ee50796d5a

Tx prefix hash: f55cfd3ead9e26dd354e999168d14eacc4fef18c81fe5040e6cbd0c8c8995a1d
Tx public key: 0edf59fcc653c19f37e68391cc28c232de2dff4fe66fe94ec6b0a0e1af117c4f
Timestamp: 1737460473 Timestamp [UCT]: 2025-01-21 11:54:33 Age [y:d:h:m:s]: 00:148:00:40:43
Block: 1202117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105540 RingCT/type: yes/0
Extra: 010edf59fcc653c19f37e68391cc28c232de2dff4fe66fe94ec6b0a0e1af117c4f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 034bfe0c4de9c62ce1cf9cf098e2d82708526cc14c7184f9fa04a8bfca34b137 0.600000000000 1688776 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": 1202127, "vin": [ { "gen": { "height": 1202117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "034bfe0c4de9c62ce1cf9cf098e2d82708526cc14c7184f9fa04a8bfca34b137" } } ], "extra": [ 1, 14, 223, 89, 252, 198, 83, 193, 159, 55, 230, 131, 145, 204, 40, 194, 50, 222, 45, 255, 79, 230, 111, 233, 78, 198, 176, 160, 225, 175, 17, 124, 79, 2, 17, 0, 0, 0, 1, 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