Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468d1168e4e945c79dc7e4d3dcd469ba753ed95079a6b0e1037cf6e2844d36d3

Tx prefix hash: 5e0b39d065f74427923077dc9122f9d1b9c3cba8a3163f3b4fe37a0545a287a8
Tx public key: 78443832759c5d477f294ba837ae0cc27b3460e50c37aecf52e93849414a1b37
Timestamp: 1578645609 Timestamp [UCT]: 2020-01-10 08:40:09 Age [y:d:h:m:s]: 05:300:02:05:51
Block: 42394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1362343 RingCT/type: yes/0
Extra: 0178443832759c5d477f294ba837ae0cc27b3460e50c37aecf52e93849414a1b3702110000000b8a2ee0d9000000000000000000

1 output(s) for total of 444.152308321000 dcy

stealth address amount amount idx
00: 6b6cd0f5b13fd87cfc297d68bbb7150faab1113e7c3df1744f53d3f14dd60b83 444.152308321000 76365 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": 42404, "vin": [ { "gen": { "height": 42394 } } ], "vout": [ { "amount": 444152308321, "target": { "key": "6b6cd0f5b13fd87cfc297d68bbb7150faab1113e7c3df1744f53d3f14dd60b83" } } ], "extra": [ 1, 120, 68, 56, 50, 117, 156, 93, 71, 127, 41, 75, 168, 55, 174, 12, 194, 123, 52, 96, 229, 12, 55, 174, 207, 82, 233, 56, 73, 65, 74, 27, 55, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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