Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a682bfb8f3d2250f0044de86b3cc577458b3093b7306065d1b1c29c53c851c4

Tx prefix hash: 2162b818f13d8a7bc8687b2ea68757ff0aae884bb773e938cbbf1c2b3232055c
Tx public key: acc1b22f1e83b4a05dfb780be1fe078e1755f001feeacf21bbf233e9252e49c1
Timestamp: 1715664799 Timestamp [UCT]: 2024-05-14 05:33:19 Age [y:d:h:m:s]: 00:336:06:41:16
Block: 1021615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240367 RingCT/type: yes/0
Extra: 01acc1b22f1e83b4a05dfb780be1fe078e1755f001feeacf21bbf233e9252e49c10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7cc9359f8968f027cc5f4b32b3b20148fe6927e29776553a7334e02edbc3f5 0.600000000000 1485984 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": 1021625, "vin": [ { "gen": { "height": 1021615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7cc9359f8968f027cc5f4b32b3b20148fe6927e29776553a7334e02edbc3f5" } } ], "extra": [ 1, 172, 193, 178, 47, 30, 131, 180, 160, 93, 251, 120, 11, 225, 254, 7, 142, 23, 85, 240, 1, 254, 234, 207, 33, 187, 242, 51, 233, 37, 46, 73, 193, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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