Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07db53fc4b5752000cf7a2a528c94fa8af5b27eb570dcffc69f9a924def2d67

Tx prefix hash: 16e959a104f6d629a175eca2fc7c77d5ea53b2b630a2c3acc61be1a34937b0d4
Tx public key: e0ef2da3d3f8640bdce2a52b3b4a53c6fa1f45a41024e7df84fc50450f1b1b57
Timestamp: 1704735156 Timestamp [UCT]: 2024-01-08 17:32:36 Age [y:d:h:m:s]: 01:309:19:42:36
Block: 930989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480262 RingCT/type: yes/0
Extra: 01e0ef2da3d3f8640bdce2a52b3b4a53c6fa1f45a41024e7df84fc50450f1b1b5702110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3efb73cfb429b909a9022e7f802de248af103600f25576316bd45dad69fd2404 0.600000000000 1388881 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": 930999, "vin": [ { "gen": { "height": 930989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3efb73cfb429b909a9022e7f802de248af103600f25576316bd45dad69fd2404" } } ], "extra": [ 1, 224, 239, 45, 163, 211, 248, 100, 11, 220, 226, 165, 43, 59, 74, 83, 198, 250, 31, 69, 164, 16, 36, 231, 223, 132, 252, 80, 69, 15, 27, 27, 87, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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