Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 827a03d88ab186f84504101fd41fee578c728de92e991ad3557f09b9d2b7ace6

Tx prefix hash: a6b528cecc2194f35f04a23afc9b0717dd6caa9a375ef6763dd1e21658a6bf8b
Tx public key: 35674ed5f37d47d4df3ab0dd7f961e3f3da8ea618384d05b84b7d8a693b113fd
Timestamp: 1681155962 Timestamp [UCT]: 2023-04-10 19:46:02 Age [y:d:h:m:s]: 01:288:00:53:26
Block: 735755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467340 RingCT/type: yes/0
Extra: 0135674ed5f37d47d4df3ab0dd7f961e3f3da8ea618384d05b84b7d8a693b113fd0211000000025029cbac000000000000000000

1 output(s) for total of 2.239435109000 dcy

stealth address amount amount idx
00: 24644a0d4243f6d5e3bbada3705d2c1bcc3ac36c8c102df199a77888078a2c6b 2.239435109000 1182108 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": 735765, "vin": [ { "gen": { "height": 735755 } } ], "vout": [ { "amount": 2239435109, "target": { "key": "24644a0d4243f6d5e3bbada3705d2c1bcc3ac36c8c102df199a77888078a2c6b" } } ], "extra": [ 1, 53, 103, 78, 213, 243, 125, 71, 212, 223, 58, 176, 221, 127, 150, 30, 63, 61, 168, 234, 97, 131, 132, 208, 91, 132, 183, 216, 166, 147, 177, 19, 253, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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