Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916be28423d3f5c929a86e60afa449ad8c4fc573c7bfe97c65913e2df01fb2b1

Tx prefix hash: 25b2671cb45e097e9e4fd2b8d2cc132ce23ce437b02f408ede9909299e1e3292
Tx public key: 7368edef94d554a447e03e925650f6a8a4b91394f89fd7fa0113be22a4fcaad2
Timestamp: 1721262727 Timestamp [UCT]: 2024-07-18 00:32:07 Age [y:d:h:m:s]: 00:246:16:48:47
Block: 1068040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176219 RingCT/type: yes/0
Extra: 017368edef94d554a447e03e925650f6a8a4b91394f89fd7fa0113be22a4fcaad202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93793ee155bd11eab27b41cb414875f2c90cb0c4cec8c9117a3eb6487b28997a 0.600000000000 1539029 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": 1068050, "vin": [ { "gen": { "height": 1068040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93793ee155bd11eab27b41cb414875f2c90cb0c4cec8c9117a3eb6487b28997a" } } ], "extra": [ 1, 115, 104, 237, 239, 148, 213, 84, 164, 71, 224, 62, 146, 86, 80, 246, 168, 164, 185, 19, 148, 248, 159, 215, 250, 1, 19, 190, 34, 164, 252, 170, 210, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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