Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcdf273ef99427b739634c7aded35574427b278eb67329f2cebaaa69c7790ade

Tx prefix hash: afd7e6c83d92feaeba38837ebd2c570efbf692f90e2ece32fa437c8b9f7b7d89
Tx public key: dcd56cfec74f64dd42b23f3fc95eee8c3dc83c467569fea92fdc4ed963f9f94e
Timestamp: 1704516141 Timestamp [UCT]: 2024-01-06 04:42:21 Age [y:d:h:m:s]: 01:308:02:50:49
Block: 929159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479057 RingCT/type: yes/0
Extra: 01dcd56cfec74f64dd42b23f3fc95eee8c3dc83c467569fea92fdc4ed963f9f94e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9468bba32db430a1e5ecb332c4cb253c91a29222f1dde191f1801365b99d4c74 0.600000000000 1387027 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": 929169, "vin": [ { "gen": { "height": 929159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9468bba32db430a1e5ecb332c4cb253c91a29222f1dde191f1801365b99d4c74" } } ], "extra": [ 1, 220, 213, 108, 254, 199, 79, 100, 221, 66, 178, 63, 63, 201, 94, 238, 140, 61, 200, 60, 70, 117, 105, 254, 169, 47, 220, 78, 217, 99, 249, 249, 78, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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