Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0492ab3667765b0ee52e84ec6e530c37cc8b8ee79e3564a404ac82df8a686101

Tx prefix hash: 62310f6acdd4c0e0cd602184d786da58054f71cc59dfb5f372831c06c5030196
Tx public key: c767fcee09af8ce5c38f33e7c52f4d27fb13687b5acf3b7c5ef220c61cb841f0
Timestamp: 1589360638 Timestamp [UCT]: 2020-05-13 09:03:58 Age [y:d:h:m:s]: 04:177:22:17:47
Block: 100140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1047507 RingCT/type: yes/0
Extra: 01c767fcee09af8ce5c38f33e7c52f4d27fb13687b5acf3b7c5ef220c61cb841f002110000000837fb5df4000000000000000000

1 output(s) for total of 285.887634756000 dcy

stealth address amount amount idx
00: 9b2fd1aa236f521e6a9985f64c822ec7a727d8a85c7e90011d73f008f9446617 285.887634756000 176592 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": 100150, "vin": [ { "gen": { "height": 100140 } } ], "vout": [ { "amount": 285887634756, "target": { "key": "9b2fd1aa236f521e6a9985f64c822ec7a727d8a85c7e90011d73f008f9446617" } } ], "extra": [ 1, 199, 103, 252, 238, 9, 175, 140, 229, 195, 143, 51, 231, 197, 47, 77, 39, 251, 19, 104, 123, 90, 207, 59, 124, 94, 242, 32, 198, 28, 184, 65, 240, 2, 17, 0, 0, 0, 8, 55, 251, 93, 244, 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