Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcac607bd82ff0f40ca476c9dc9f3b734b5efd50dc721bd80c51b633f50eaf4

Tx prefix hash: 381fd0254093c4ad584934db3d8852605291be8343105181a63d4343e25d1297
Tx public key: af91b3321f68d24a711ae8c44d58be974830c0d032eab4107862cafed9019171
Timestamp: 1706706714 Timestamp [UCT]: 2024-01-31 13:11:54 Age [y:d:h:m:s]: 01:140:21:45:21
Block: 947334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361667 RingCT/type: yes/0
Extra: 01af91b3321f68d24a711ae8c44d58be974830c0d032eab4107862cafed9019171021100000008c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb040590c5a825c471458e89d0eab9fa8f1d8043f0eb0664f4ba6c306c0b56a7 0.600000000000 1405682 of 15

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": 947344, "vin": [ { "gen": { "height": 947334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb040590c5a825c471458e89d0eab9fa8f1d8043f0eb0664f4ba6c306c0b56a7" } } ], "extra": [ 1, 175, 145, 179, 50, 31, 104, 210, 74, 113, 26, 232, 196, 77, 88, 190, 151, 72, 48, 192, 208, 50, 234, 180, 16, 120, 98, 202, 254, 217, 1, 145, 113, 2, 17, 0, 0, 0, 8, 197, 69, 41, 96, 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