Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5737b14207b6bd951d83ab9433eebad4e1de7adf35fdc4b7b8175c678af3d6b3

Tx prefix hash: e24b34f19b007bb6902710d6c52b781005edc8508f9176b869d898d3ad85597c
Tx public key: 58b67d1aae8ed928012547b6e204cf0d3c99eb7c3bd12b07a10c6035e44c86dd
Timestamp: 1722947370 Timestamp [UCT]: 2024-08-06 12:29:30 Age [y:d:h:m:s]: 00:250:05:07:44
Block: 1081987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178728 RingCT/type: yes/0
Extra: 0158b67d1aae8ed928012547b6e204cf0d3c99eb7c3bd12b07a10c6035e44c86dd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69e442561c99214245b7d0b7e23ea81c8ad36e95274779a3c2181ed474de3a04 0.600000000000 1555810 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": 1081997, "vin": [ { "gen": { "height": 1081987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69e442561c99214245b7d0b7e23ea81c8ad36e95274779a3c2181ed474de3a04" } } ], "extra": [ 1, 88, 182, 125, 26, 174, 142, 217, 40, 1, 37, 71, 182, 226, 4, 207, 13, 60, 153, 235, 124, 59, 209, 43, 7, 161, 12, 96, 53, 228, 76, 134, 221, 2, 17, 0, 0, 0, 6, 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