Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6a78857a5f74a05f2f8e5e33108b2b5402fb7e677f19f111ebf1bf90b9adf50

Tx prefix hash: 2829338e9201e502748b674c1e8a72ef042b912e72f06825d8632291be363ca4
Tx public key: e3bfcd71730401181d8c0e4a6463c3339c2f2acd80a019ab66110dea69892962
Timestamp: 1709859910 Timestamp [UCT]: 2024-03-08 01:05:10 Age [y:d:h:m:s]: 01:101:12:38:18
Block: 973497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333487 RingCT/type: yes/0
Extra: 01e3bfcd71730401181d8c0e4a6463c3339c2f2acd80a019ab66110dea6989296202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a22a431f14d93fdb49fbfaef70f02bcf5a1ccbc77e59ac0bf12f78d66fe412c1 0.600000000000 1433432 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": 973507, "vin": [ { "gen": { "height": 973497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a22a431f14d93fdb49fbfaef70f02bcf5a1ccbc77e59ac0bf12f78d66fe412c1" } } ], "extra": [ 1, 227, 191, 205, 113, 115, 4, 1, 24, 29, 140, 14, 74, 100, 99, 195, 51, 156, 47, 42, 205, 128, 160, 25, 171, 102, 17, 13, 234, 105, 137, 41, 98, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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