Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739d31552c081a586e2f5753bf6a46f97976c561d64343280db5ac5d303ace1e

Tx prefix hash: dd3c2cfa010b8e4efcc62f03680d0be098999977cdb3263be6d4030715178a04
Tx public key: bb1d5f6ba5a74cd2dbb23d5c54db33008fceecd80c38dad50de4fb7ef6a1d7f6
Timestamp: 1661024638 Timestamp [UCT]: 2022-08-20 19:43:58 Age [y:d:h:m:s]: 02:241:14:30:21
Block: 570146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 693928 RingCT/type: yes/0
Extra: 01bb1d5f6ba5a74cd2dbb23d5c54db33008fceecd80c38dad50de4fb7ef6a1d7f602110000000f75e3f0e9000000000000000000

1 output(s) for total of 7.922636417000 dcy

stealth address amount amount idx
00: 21e79ef838859f85730d4c16d93d88a4a71d1dc9456f72d4d3da8e0907c9d4f6 7.922636417000 1003317 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": 570156, "vin": [ { "gen": { "height": 570146 } } ], "vout": [ { "amount": 7922636417, "target": { "key": "21e79ef838859f85730d4c16d93d88a4a71d1dc9456f72d4d3da8e0907c9d4f6" } } ], "extra": [ 1, 187, 29, 95, 107, 165, 167, 76, 210, 219, 178, 61, 92, 84, 219, 51, 0, 143, 206, 236, 216, 12, 56, 218, 213, 13, 228, 251, 126, 246, 161, 215, 246, 2, 17, 0, 0, 0, 15, 117, 227, 240, 233, 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