Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e00742abd5798baf323a06946bfb90d9245e23d28ab920e66f8fc41865b5536

Tx prefix hash: 1c8a8da7acc6f918c07df3d455dd23b88cbbdaff86a0ad931a9b10c9b7e0aa7e
Tx public key: 45c371567729f51b23c54676624fe8c9270a9baac12ac26bf6c19838879399af
Timestamp: 1632261471 Timestamp [UCT]: 2021-09-21 21:57:51 Age [y:d:h:m:s]: 03:108:16:31:06
Block: 338377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 853850 RingCT/type: yes/0
Extra: 0145c371567729f51b23c54676624fe8c9270a9baac12ac26bf6c19838879399af0211000000ba5d7cc334000000000000000000

1 output(s) for total of 46.431954646000 dcy

stealth address amount amount idx
00: 376c762f1e61cd18c650cb1fe718c4b6b345e71255ccb9e3166c53a6c211122b 46.431954646000 696426 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": 338387, "vin": [ { "gen": { "height": 338377 } } ], "vout": [ { "amount": 46431954646, "target": { "key": "376c762f1e61cd18c650cb1fe718c4b6b345e71255ccb9e3166c53a6c211122b" } } ], "extra": [ 1, 69, 195, 113, 86, 119, 41, 245, 27, 35, 197, 70, 118, 98, 79, 232, 201, 39, 10, 155, 170, 193, 42, 194, 107, 246, 193, 152, 56, 135, 147, 153, 175, 2, 17, 0, 0, 0, 186, 93, 124, 195, 52, 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