Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eef6913667db22a5d8bd631bf88a38fc1b4e73cec2c483639322ce4184d6e10

Tx prefix hash: 93aebfd4d9ca207aa9b731b7653854f664e25cd034832aa6d8d847a52119e66c
Tx public key: 27d98615b3e577b88d301f28211d85479fa92be8680c6f2917d6e1f957fd918e
Timestamp: 1725785021 Timestamp [UCT]: 2024-09-08 08:43:41 Age [y:d:h:m:s]: 00:211:06:32:56
Block: 1105512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150838 RingCT/type: yes/0
Extra: 0127d98615b3e577b88d301f28211d85479fa92be8680c6f2917d6e1f957fd918e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd279b5c346bb796f13c87739845be515866660fe35c4aa7afb128c884a6cb9 0.600000000000 1582867 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": 1105522, "vin": [ { "gen": { "height": 1105512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd279b5c346bb796f13c87739845be515866660fe35c4aa7afb128c884a6cb9" } } ], "extra": [ 1, 39, 217, 134, 21, 179, 229, 119, 184, 141, 48, 31, 40, 33, 29, 133, 71, 159, 169, 43, 232, 104, 12, 111, 41, 23, 214, 225, 249, 87, 253, 145, 142, 2, 17, 0, 0, 0, 4, 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