Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef4f683830be1a15ed88f204c58b7a691d076081b89475d04ee402e1212ae0c2

Tx prefix hash: 4aa088b8982c5e9cccaa57a42680c746a1ecaba1c912d1ef43917b954c4dbcf8
Tx public key: 70c49059f57674f318bc667b9619351c3b15ef34fbb0c836140e9917c0f78b19
Timestamp: 1713541242 Timestamp [UCT]: 2024-04-19 15:40:42 Age [y:d:h:m:s]: 00:155:07:51:49
Block: 1004005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111266 RingCT/type: yes/0
Extra: 0170c49059f57674f318bc667b9619351c3b15ef34fbb0c836140e9917c0f78b1902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 903cfa0d30f6e5528b8c96e55e477e50c2e378b5175b02ed572b31f924c62792 0.600000000000 1464561 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": 1004015, "vin": [ { "gen": { "height": 1004005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "903cfa0d30f6e5528b8c96e55e477e50c2e378b5175b02ed572b31f924c62792" } } ], "extra": [ 1, 112, 196, 144, 89, 245, 118, 116, 243, 24, 188, 102, 123, 150, 25, 53, 28, 59, 21, 239, 52, 251, 176, 200, 54, 20, 14, 153, 23, 192, 247, 139, 25, 2, 17, 0, 0, 0, 7, 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