Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398fc23d9e37ea7b7c9db11a44db23fe033e6aed9da2a05611ff3abb0c12ca3e

Tx prefix hash: ae65a67ada12f4153407d694777206e49497e1f648575f88984bf47140b48b0c
Tx public key: bfe60da2f76451075b5938d0741b0ef3485423f6a31e0c1c1883e2eb8b737a8b
Timestamp: 1727124577 Timestamp [UCT]: 2024-09-23 20:49:37 Age [y:d:h:m:s]: 00:213:08:36:53
Block: 1116619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152320 RingCT/type: yes/0
Extra: 01bfe60da2f76451075b5938d0741b0ef3485423f6a31e0c1c1883e2eb8b737a8b02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c89ce9ddb1c0acbbbc58f6e13237eb67d4e6e84500cd2eb1d7b10ff66e57968 0.600000000000 1597168 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": 1116629, "vin": [ { "gen": { "height": 1116619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c89ce9ddb1c0acbbbc58f6e13237eb67d4e6e84500cd2eb1d7b10ff66e57968" } } ], "extra": [ 1, 191, 230, 13, 162, 247, 100, 81, 7, 91, 89, 56, 208, 116, 27, 14, 243, 72, 84, 35, 246, 163, 30, 12, 28, 24, 131, 226, 235, 139, 115, 122, 139, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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