Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a880674583d87350cacd15d50ac91c9c4e2fcc67d39de912403cf15a0ce0aaaa

Tx prefix hash: adb505986645d4a69bf2c89c362f03770a2c49bda556e7d9fedb10d0dfff4ef5
Tx public key: 00427e2764c376c518f6c519e801277a7945f86c03fa2f1bfa991f4ebdf29091
Timestamp: 1764509526 Timestamp [UCT]: 2025-11-30 13:32:06 Age [y:d:h:m:s]: 00:000:04:49:46
Block: 1423436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144 RingCT/type: yes/0
Extra: 0100427e2764c376c518f6c519e801277a7945f86c03fa2f1bfa991f4ebdf29091021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a68a28af8e089fcea3ef9b190b40b5f472906ce997b8b9ac5f6b90f4fde02a3f 0.600000000000 1912047 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": 1423446, "vin": [ { "gen": { "height": 1423436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a68a28af8e089fcea3ef9b190b40b5f472906ce997b8b9ac5f6b90f4fde02a3f" } } ], "extra": [ 1, 0, 66, 126, 39, 100, 195, 118, 197, 24, 246, 197, 25, 232, 1, 39, 122, 121, 69, 248, 108, 3, 250, 47, 27, 250, 153, 31, 78, 189, 242, 144, 145, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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