Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea8b4c566944f870ba2726c68831eb1c121a3411493bd58660772f0ed17ca2a

Tx prefix hash: 48d168b7b6ee9ce35e8c060bce944d29666b9f14377274bb117e1f841e0766dc
Tx public key: 6d6dec9bc5b7c479e11ec8aea3713aea19ef9f0d9c0b6aa68cd02c39cc4fb717
Timestamp: 1693914250 Timestamp [UCT]: 2023-09-05 11:44:10 Age [y:d:h:m:s]: 01:270:01:22:31
Block: 841475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454174 RingCT/type: yes/0
Extra: 016d6dec9bc5b7c479e11ec8aea3713aea19ef9f0d9c0b6aa68cd02c39cc4fb71702110000000875e3f0e9000000000000000000

1 output(s) for total of 0.999641048000 dcy

stealth address amount amount idx
00: 3f423b5d8a45b319eaf07ebe32fd2f15a02fd9fd55e7ce98a8d450ea7d6233ab 0.999641048000 1294511 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": 841485, "vin": [ { "gen": { "height": 841475 } } ], "vout": [ { "amount": 999641048, "target": { "key": "3f423b5d8a45b319eaf07ebe32fd2f15a02fd9fd55e7ce98a8d450ea7d6233ab" } } ], "extra": [ 1, 109, 109, 236, 155, 197, 183, 196, 121, 225, 30, 200, 174, 163, 113, 58, 234, 25, 239, 159, 13, 156, 11, 106, 166, 140, 208, 44, 57, 204, 79, 183, 23, 2, 17, 0, 0, 0, 8, 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