Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435c26bffe5e881b2410ee4bef791ca5dfa187c5d065b491071a2a2b44f5a413

Tx prefix hash: ab4d28195b254538f2c1f87eeb266e55fb4cf86a5000e4dfb093c537d914b2ac
Tx public key: 953254dbd713459161019358b527e851fba054ff93de1f5b88d5975bd0609037
Timestamp: 1694292382 Timestamp [UCT]: 2023-09-09 20:46:22 Age [y:d:h:m:s]: 02:088:02:22:31
Block: 844612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582675 RingCT/type: yes/0
Extra: 01953254dbd713459161019358b527e851fba054ff93de1f5b88d5975bd060903702110000000975e3f0e9000000000000000000

1 output(s) for total of 0.976000170000 dcy

stealth address amount amount idx
00: ea67a956b484885f5850715c4acd3ed800ad9d4605d1778892ba6b2b3ee108bc 0.976000170000 1297932 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": 844622, "vin": [ { "gen": { "height": 844612 } } ], "vout": [ { "amount": 976000170, "target": { "key": "ea67a956b484885f5850715c4acd3ed800ad9d4605d1778892ba6b2b3ee108bc" } } ], "extra": [ 1, 149, 50, 84, 219, 215, 19, 69, 145, 97, 1, 147, 88, 181, 39, 232, 81, 251, 160, 84, 255, 147, 222, 31, 91, 136, 213, 151, 91, 208, 96, 144, 55, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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