Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0f32a800b969c7b9c06d86d9b17d2fe8bf4c446878f89333ab81f90aed287b

Tx prefix hash: 2bc27c66e6dc7bc4c677f3af97349fff1b18294c926efd7f184a5cfb18073fbd
Tx public key: 66fddb13af3ebd64c860a503ed6399413d08522669f974ffb727142e13a79e75
Timestamp: 1726090352 Timestamp [UCT]: 2024-09-11 21:32:32 Age [y:d:h:m:s]: 00:041:07:05:34
Block: 1108041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29555 RingCT/type: yes/0
Extra: 0166fddb13af3ebd64c860a503ed6399413d08522669f974ffb727142e13a79e75021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45f07a64ddbfa46a94ed64560a55b1cb67252b44b0bcd71db8e0dfd8deb0e166 0.600000000000 1585798 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": 1108051, "vin": [ { "gen": { "height": 1108041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45f07a64ddbfa46a94ed64560a55b1cb67252b44b0bcd71db8e0dfd8deb0e166" } } ], "extra": [ 1, 102, 253, 219, 19, 175, 62, 189, 100, 200, 96, 165, 3, 237, 99, 153, 65, 61, 8, 82, 38, 105, 249, 116, 255, 183, 39, 20, 46, 19, 167, 158, 117, 2, 17, 0, 0, 0, 2, 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