Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e36c4101635cd4af950e9bf39533f18bfc6742d180260ee2a4a8b240ee4fd4

Tx prefix hash: fc8f7c908f1b2c5db058861ed23d2c12950385d8ee3bd30514154b947e85966d
Tx public key: ea1b0208b7c0b12c09c4d361fef4c5fd6a3e171461aadb18d3064e895b619a15
Timestamp: 1734139235 Timestamp [UCT]: 2024-12-14 01:20:35 Age [y:d:h:m:s]: 00:185:23:52:30
Block: 1174681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132637 RingCT/type: yes/0
Extra: 01ea1b0208b7c0b12c09c4d361fef4c5fd6a3e171461aadb18d3064e895b619a150211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd93df980b40493c3eed59c5034690e0f7b19bbe0509bab3b3ede5168b9b767 0.600000000000 1660866 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": 1174691, "vin": [ { "gen": { "height": 1174681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd93df980b40493c3eed59c5034690e0f7b19bbe0509bab3b3ede5168b9b767" } } ], "extra": [ 1, 234, 27, 2, 8, 183, 192, 177, 44, 9, 196, 211, 97, 254, 244, 197, 253, 106, 62, 23, 20, 97, 170, 219, 24, 211, 6, 78, 137, 91, 97, 154, 21, 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