Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e11eccb02e54808423b9a517d9275db4dcb94f441db840ef0d3045a791c4a08

Tx prefix hash: 215a09a03ff483814da5d8fabe0c1c0a86f3197537b5569447f92e05d4e86629
Tx public key: efc9858b76aefd24c695c221a8d528802724631daf3f09e590841a5a3bcacdf1
Timestamp: 1736377555 Timestamp [UCT]: 2025-01-08 23:05:55 Age [y:d:h:m:s]: 00:163:22:55:07
Block: 1193198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116833 RingCT/type: yes/0
Extra: 01efc9858b76aefd24c695c221a8d528802724631daf3f09e590841a5a3bcacdf10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19d05b47e9e250ec431d248d017d395d13156910f3cd74380fd06c8f57d7b55a 0.600000000000 1679757 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": 1193208, "vin": [ { "gen": { "height": 1193198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19d05b47e9e250ec431d248d017d395d13156910f3cd74380fd06c8f57d7b55a" } } ], "extra": [ 1, 239, 201, 133, 139, 118, 174, 253, 36, 198, 149, 194, 33, 168, 213, 40, 128, 39, 36, 99, 29, 175, 63, 9, 229, 144, 132, 26, 90, 59, 202, 205, 241, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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