Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb9f037754f8ac975fe8dcfb191a645af06f53c800c86d7ac8cc29fdbf9fa98

Tx prefix hash: 56ef2a417e1bf894a6ac2bafd1d9012880bc422ed333ea9a276b42c5228b6e75
Tx public key: c564605f59fc47abd376ada8c2493f061e54029bb4507d61426e7112707a41e8
Timestamp: 1684882024 Timestamp [UCT]: 2023-05-23 22:47:04 Age [y:d:h:m:s]: 01:319:12:02:26
Block: 766662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489547 RingCT/type: yes/0
Extra: 01c564605f59fc47abd376ada8c2493f061e54029bb4507d61426e7112707a41e8021100000004faf35c9c000000000000000000

1 output(s) for total of 1.769011744000 dcy

stealth address amount amount idx
00: e7b11b43009fb278bd160faf318afe1efce1f09e1ca40e58b064dbb0fcf08e17 1.769011744000 1215717 of 0

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": 766672, "vin": [ { "gen": { "height": 766662 } } ], "vout": [ { "amount": 1769011744, "target": { "key": "e7b11b43009fb278bd160faf318afe1efce1f09e1ca40e58b064dbb0fcf08e17" } } ], "extra": [ 1, 197, 100, 96, 95, 89, 252, 71, 171, 211, 118, 173, 168, 194, 73, 63, 6, 30, 84, 2, 155, 180, 80, 125, 97, 66, 110, 113, 18, 112, 122, 65, 232, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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