Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f054ac9b94ca9f80010f669bc11eca47c5482c0773ce62dfa4d2996859be8c

Tx prefix hash: 632c8773fd7c2b03c7e4eedfdfdb8c5485983a06bd48311821356b4eac7c075f
Tx public key: 008964e32b6abe9e467e98cb6a0d971a6fc8a24df8c2b7e16682fed1426959a5
Timestamp: 1706436918 Timestamp [UCT]: 2024-01-28 10:15:18 Age [y:d:h:m:s]: 01:310:18:46:04
Block: 945085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480956 RingCT/type: yes/0
Extra: 01008964e32b6abe9e467e98cb6a0d971a6fc8a24df8c2b7e16682fed1426959a502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d6ca0a525541002471a22d754ceb7c374741dfccd6c09654a8b754706204f20 0.600000000000 1403393 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": 945095, "vin": [ { "gen": { "height": 945085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d6ca0a525541002471a22d754ceb7c374741dfccd6c09654a8b754706204f20" } } ], "extra": [ 1, 0, 137, 100, 227, 43, 106, 190, 158, 70, 126, 152, 203, 106, 13, 151, 26, 111, 200, 162, 77, 248, 194, 183, 225, 102, 130, 254, 209, 66, 105, 89, 165, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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