Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8f058a595b1de5625a8c51a170736fe0c69388f0544c2eb8931fa4bf3ac3baa

Tx prefix hash: 674ed34b204de9f144fc6de90f0aa912f0226bd0fbb7f55eca845d6bc5760402
Tx public key: 114843095ea7eb81f7a7f8d1adb897a0dacabae9f6a3e89938085fbe1c85a199
Timestamp: 1608650198 Timestamp [UCT]: 2020-12-22 15:16:38 Age [y:d:h:m:s]: 03:332:02:16:54
Block: 167160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 989369 RingCT/type: yes/0
Extra: 01114843095ea7eb81f7a7f8d1adb897a0dacabae9f6a3e89938085fbe1c85a1990211000002cedf1e48bb000000000000000000

1 output(s) for total of 171.453181728000 dcy

stealth address amount amount idx
00: e38aaf90d5025a51013a195326adbdec2205d3ae011a2d58c32db37764913cf9 171.453181728000 307683 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": 167170, "vin": [ { "gen": { "height": 167160 } } ], "vout": [ { "amount": 171453181728, "target": { "key": "e38aaf90d5025a51013a195326adbdec2205d3ae011a2d58c32db37764913cf9" } } ], "extra": [ 1, 17, 72, 67, 9, 94, 167, 235, 129, 247, 167, 248, 209, 173, 184, 151, 160, 218, 202, 186, 233, 246, 163, 232, 153, 56, 8, 95, 190, 28, 133, 161, 153, 2, 17, 0, 0, 2, 206, 223, 30, 72, 187, 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