Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04cdaeb8220ff3a0499f12bb7d46335cba73df4fa72da137bafa5441ded867d7

Tx prefix hash: 3c5222efae4e7c4e7fff792ba5e92022a55af7e83a2a57b5b887502c508d0d4f
Tx public key: 6eb4c049dabf4997b0c8917ce49d5ed275695b850f2b10bfcb2b5206ab9c97a1
Timestamp: 1721052890 Timestamp [UCT]: 2024-07-15 14:14:50 Age [y:d:h:m:s]: 00:264:00:06:35
Block: 1066299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188594 RingCT/type: yes/0
Extra: 016eb4c049dabf4997b0c8917ce49d5ed275695b850f2b10bfcb2b5206ab9c97a1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1026564a84a42d899afdf2bd130917fa98a1c9353cabd555031b98c9cc5d262f 0.600000000000 1536872 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": 1066309, "vin": [ { "gen": { "height": 1066299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1026564a84a42d899afdf2bd130917fa98a1c9353cabd555031b98c9cc5d262f" } } ], "extra": [ 1, 110, 180, 192, 73, 218, 191, 73, 151, 176, 200, 145, 124, 228, 157, 94, 210, 117, 105, 91, 133, 15, 43, 16, 191, 203, 43, 82, 6, 171, 156, 151, 161, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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