Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962108c7d862c812dc6c3cf7165ad17f7ea6406b0741f0b5b4d0baf78ad5963d

Tx prefix hash: 5d1a28952732202b543948e02961e922abddf1097069ad2efb3569f84d3049af
Tx public key: a29f7c5f52df301a31751344c3ef372fbd3a2de5360d189fe0f8f3cf54520948
Timestamp: 1644993546 Timestamp [UCT]: 2022-02-16 06:39:06 Age [y:d:h:m:s]: 03:263:09:09:59
Block: 439688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 965902 RingCT/type: yes/0
Extra: 01a29f7c5f52df301a31751344c3ef372fbd3a2de5360d189fe0f8f3cf545209480211000000035eb576c5000000000000000000

1 output(s) for total of 21.435391833000 dcy

stealth address amount amount idx
00: 8cd244798942890b80af38b0a75fa82e4d6cab3ae8c747302ba84af462c21891 21.435391833000 851867 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": 439698, "vin": [ { "gen": { "height": 439688 } } ], "vout": [ { "amount": 21435391833, "target": { "key": "8cd244798942890b80af38b0a75fa82e4d6cab3ae8c747302ba84af462c21891" } } ], "extra": [ 1, 162, 159, 124, 95, 82, 223, 48, 26, 49, 117, 19, 68, 195, 239, 55, 47, 189, 58, 45, 229, 54, 13, 24, 159, 224, 248, 243, 207, 84, 82, 9, 72, 2, 17, 0, 0, 0, 3, 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