Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc78a860abac7d340f602789b7764f510e4be58e83d1860e9e1b0a3ed63787f5

Tx prefix hash: d49f01fdb9ad770efe9fd2501ce3b0dd28d20c0fa1a058fb88259c243f3b96da
Tx public key: 1246d9f64dbef1ac0c3f273bb85fa35306de1c1662d0d36270bc6b99e162a0b5
Timestamp: 1635550570 Timestamp [UCT]: 2021-10-29 23:36:10 Age [y:d:h:m:s]: 03:204:17:36:58
Block: 363250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924651 RingCT/type: yes/0
Extra: 011246d9f64dbef1ac0c3f273bb85fa35306de1c1662d0d36270bc6b99e162a0b502110000000f1154028c000000000000000000

1 output(s) for total of 38.406290446000 dcy

stealth address amount amount idx
00: a1fec2087b7ced6ae3a0347fb34ac87f2f363565e03a95237e28e2a29f27b4e6 38.406290446000 738370 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": 363260, "vin": [ { "gen": { "height": 363250 } } ], "vout": [ { "amount": 38406290446, "target": { "key": "a1fec2087b7ced6ae3a0347fb34ac87f2f363565e03a95237e28e2a29f27b4e6" } } ], "extra": [ 1, 18, 70, 217, 246, 77, 190, 241, 172, 12, 63, 39, 59, 184, 95, 163, 83, 6, 222, 28, 22, 98, 208, 211, 98, 112, 188, 107, 153, 225, 98, 160, 181, 2, 17, 0, 0, 0, 15, 17, 84, 2, 140, 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