Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a57444699e2e57c45d58a558be4efdf8882fe0ca7e93d7a2a7165a6550489146

Tx prefix hash: 21682c36332bf9bf2829f883ccb48cebf88942e5749e2de3829a7eb3c79bdc2d
Tx public key: 5f35ccb63cd8ab7bc52be8c1b81da44e4582c4252d0fcc246a7a3da32b34b887
Timestamp: 1736260768 Timestamp [UCT]: 2025-01-07 14:39:28 Age [y:d:h:m:s]: 01:001:15:09:21
Block: 1192233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259614 RingCT/type: yes/0
Extra: 015f35ccb63cd8ab7bc52be8c1b81da44e4582c4252d0fcc246a7a3da32b34b887021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29fda7d1ac3b7893c407b8318cad0d5c189b3631e9a34602ac7a0935760c3dbf 0.600000000000 1678782 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": 1192243, "vin": [ { "gen": { "height": 1192233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29fda7d1ac3b7893c407b8318cad0d5c189b3631e9a34602ac7a0935760c3dbf" } } ], "extra": [ 1, 95, 53, 204, 182, 60, 216, 171, 123, 197, 43, 232, 193, 184, 29, 164, 78, 69, 130, 196, 37, 45, 15, 204, 36, 106, 122, 61, 163, 43, 52, 184, 135, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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