Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738b638018e44a2150c3f5982cea40068e856d53eee8623eed62b07ad2a89245

Tx prefix hash: 270ab41b318f554426bcc9b3492c605e6f891ff34cac15659f54542034c05d90
Tx public key: b08024142d7852aa9f84682b66dd923c330d282f2075dee8330cf0c1a1eeb2a5
Timestamp: 1612919234 Timestamp [UCT]: 2021-02-10 01:07:14 Age [y:d:h:m:s]: 04:013:22:10:07
Block: 195576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1029521 RingCT/type: yes/0
Extra: 01b08024142d7852aa9f84682b66dd923c330d282f2075dee8330cf0c1a1eeb2a50211000003df4ea414e5000000000000000000

1 output(s) for total of 138.030847301000 dcy

stealth address amount amount idx
00: 3e1521f5617911359bd118da01bb0568a792693b771bb21915d6a6d0e230340b 138.030847301000 398170 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": 195586, "vin": [ { "gen": { "height": 195576 } } ], "vout": [ { "amount": 138030847301, "target": { "key": "3e1521f5617911359bd118da01bb0568a792693b771bb21915d6a6d0e230340b" } } ], "extra": [ 1, 176, 128, 36, 20, 45, 120, 82, 170, 159, 132, 104, 43, 102, 221, 146, 60, 51, 13, 40, 47, 32, 117, 222, 232, 51, 12, 240, 193, 161, 238, 178, 165, 2, 17, 0, 0, 3, 223, 78, 164, 20, 229, 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