Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10abdf52f575be3ad6216b54bfceafb658a7c3aae8d496ed78fae5a22aab681

Tx prefix hash: 8db5ecc78ed6feeabdfd59627a5153f6ba83967d71880a8f8ad591e01f636e9f
Tx public key: fcac69e8013c9e84dfa143a39f11f7db85beb26528adce604876e5b1e0b9a90c
Timestamp: 1730053495 Timestamp [UCT]: 2024-10-27 18:24:55 Age [y:d:h:m:s]: 00:087:00:55:18
Block: 1140866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62184 RingCT/type: yes/0
Extra: 01fcac69e8013c9e84dfa143a39f11f7db85beb26528adce604876e5b1e0b9a90c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e49f91d1c2a3c2aed62eb18732772b1fce53fa4451f3cefe8894021f5d5c4621 0.600000000000 1624669 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": 1140876, "vin": [ { "gen": { "height": 1140866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e49f91d1c2a3c2aed62eb18732772b1fce53fa4451f3cefe8894021f5d5c4621" } } ], "extra": [ 1, 252, 172, 105, 232, 1, 60, 158, 132, 223, 161, 67, 163, 159, 17, 247, 219, 133, 190, 178, 101, 40, 173, 206, 96, 72, 118, 229, 177, 224, 185, 169, 12, 2, 17, 0, 0, 0, 4, 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