Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e6190861404003fc4bda5b6d89c9d7b50967d4c3ce6463f668fb0bcd2665fb

Tx prefix hash: 2eb6d7ea752f2060a51c29775faecc8bb7cffb14fce945c5fd42d66c96771f19
Tx public key: b7005477dcae6c20d9aed59e1d40877482b17eeb9d69a930dd16ba9415c48751
Timestamp: 1734136898 Timestamp [UCT]: 2024-12-14 00:41:38 Age [y:d:h:m:s]: 00:329:07:16:02
Block: 1174663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232852 RingCT/type: yes/0
Extra: 01b7005477dcae6c20d9aed59e1d40877482b17eeb9d69a930dd16ba9415c48751021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b1e7ef8c206648014c62ce84e018ec035dca34f0e83313d232ff2ed13b5f87 0.600000000000 1660844 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": 1174673, "vin": [ { "gen": { "height": 1174663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b1e7ef8c206648014c62ce84e018ec035dca34f0e83313d232ff2ed13b5f87" } } ], "extra": [ 1, 183, 0, 84, 119, 220, 174, 108, 32, 217, 174, 213, 158, 29, 64, 135, 116, 130, 177, 126, 235, 157, 105, 169, 48, 221, 22, 186, 148, 21, 196, 135, 81, 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