Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e232c81f3e53c36410aac11ab078376ec1487faa85e2243ba7e18dc7611eba2f

Tx prefix hash: 5a9be1a906ba2edab1804fc450ff5e9578e2e64fb50795bc89716dcc5ce7e768
Tx public key: 99cfea66a787c93818cb04284cf2bdd6740fc845d4a1c4e8d502819da0a3067a
Timestamp: 1727935336 Timestamp [UCT]: 2024-10-03 06:02:16 Age [y:d:h:m:s]: 00:052:11:59:28
Block: 1123347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37503 RingCT/type: yes/0
Extra: 0199cfea66a787c93818cb04284cf2bdd6740fc845d4a1c4e8d502819da0a3067a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57bb663871a56c71a7106fd65c94a2cf1213a16426ef9a68c44f669be0d6185b 0.600000000000 1605880 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": 1123357, "vin": [ { "gen": { "height": 1123347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57bb663871a56c71a7106fd65c94a2cf1213a16426ef9a68c44f669be0d6185b" } } ], "extra": [ 1, 153, 207, 234, 102, 167, 135, 201, 56, 24, 203, 4, 40, 76, 242, 189, 214, 116, 15, 200, 69, 212, 161, 196, 232, 213, 2, 129, 157, 160, 163, 6, 122, 2, 17, 0, 0, 0, 3, 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