Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f0c0a7190134ba4db1b7055b0533f5ebb23d4d41bb7d221d1e76a68d90a3a5

Tx prefix hash: 310de6a720cd1f2372fc6707da333fa83869f63853ffa71aca8bf4cfc517a7a7
Tx public key: b36ed03eb24015e8b4f0aa2437777ffbfe93c5549e6b91c281bde64c52093886
Timestamp: 1650867963 Timestamp [UCT]: 2022-04-25 06:26:03 Age [y:d:h:m:s]: 02:327:04:43:29
Block: 487636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753596 RingCT/type: yes/0
Extra: 01b36ed03eb24015e8b4f0aa2437777ffbfe93c5549e6b91c281bde64c5209388602110000000f5eb576c5000000000000000000

1 output(s) for total of 14.868245667000 dcy

stealth address amount amount idx
00: 91166b9feb935a35ad90ba37dd0d35497b6e9129ce0f7d929543b8ae8a41d219 14.868245667000 910141 of 0

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": 487646, "vin": [ { "gen": { "height": 487636 } } ], "vout": [ { "amount": 14868245667, "target": { "key": "91166b9feb935a35ad90ba37dd0d35497b6e9129ce0f7d929543b8ae8a41d219" } } ], "extra": [ 1, 179, 110, 208, 62, 178, 64, 21, 232, 180, 240, 170, 36, 55, 119, 127, 251, 254, 147, 197, 84, 158, 107, 145, 194, 129, 189, 230, 76, 82, 9, 56, 134, 2, 17, 0, 0, 0, 15, 94, 181, 118, 197, 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