Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff3200a4461db79db0319802da9b2fba9b9b39d6037b0f91c46423256d126e2

Tx prefix hash: b7748d672938bef5de45fbe3ffff484bae228c931739e33f12b4df6aa6ef9b9a
Tx public key: 052acf8dbcb220c3b57e5715ded623752be1118280a46f0f1cb0e8f13e72c89d
Timestamp: 1764515059 Timestamp [UCT]: 2025-11-30 15:04:19 Age [y:d:h:m:s]: 00:058:13:50:34
Block: 1423474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41764 RingCT/type: yes/0
Extra: 01052acf8dbcb220c3b57e5715ded623752be1118280a46f0f1cb0e8f13e72c89d021100000004defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f34a35040ab2d9c212cbb47e8b460668ab222ed366178502f19c8049b7b7ae14 0.600000000000 1912087 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": 1423484, "vin": [ { "gen": { "height": 1423474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f34a35040ab2d9c212cbb47e8b460668ab222ed366178502f19c8049b7b7ae14" } } ], "extra": [ 1, 5, 42, 207, 141, 188, 178, 32, 195, 181, 126, 87, 21, 222, 214, 35, 117, 43, 225, 17, 130, 128, 164, 111, 15, 28, 176, 232, 241, 62, 114, 200, 157, 2, 17, 0, 0, 0, 4, 222, 251, 143, 24, 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