Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4048d50b57ea67b53cf5d554279ea52680c87b0e48cd12f3197fd2d83f1c53c

Tx prefix hash: 4eed0e2ef809e97c3001000cdfdccb8c7195ae328f0d114bbaf86342abacc40c
Tx public key: db3fa209f6612bfbcd6bd58a2ff87a17598bc8524d39cf84b951048f6a6b1f31
Timestamp: 1708095975 Timestamp [UCT]: 2024-02-16 15:06:15 Age [y:d:h:m:s]: 00:331:11:29:54
Block: 958866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237292 RingCT/type: yes/0
Extra: 01db3fa209f6612bfbcd6bd58a2ff87a17598bc8524d39cf84b951048f6a6b1f310211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4753c8da419894be8bb70ac7a1c2e71b6750216344ab934e73a741d98b1f289e 0.600000000000 1418281 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": 958876, "vin": [ { "gen": { "height": 958866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4753c8da419894be8bb70ac7a1c2e71b6750216344ab934e73a741d98b1f289e" } } ], "extra": [ 1, 219, 63, 162, 9, 246, 97, 43, 251, 205, 107, 213, 138, 47, 248, 122, 23, 89, 139, 200, 82, 77, 57, 207, 132, 185, 81, 4, 143, 106, 107, 31, 49, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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