Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42470dc451747ad5c25c996bf102da9d9c484845c8a257fafb81fb223aa5159e

Tx prefix hash: a5a11501f69c11d178cd450921562ce799c603b24c8555464638e80213f09edd
Tx public key: cbae7d4c98cb93bd6da6255c7f1fe2badd3ef8494155a02a76d7afed10d14110
Timestamp: 1719694748 Timestamp [UCT]: 2024-06-29 20:59:08 Age [y:d:h:m:s]: 00:282:09:32:40
Block: 1055011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201783 RingCT/type: yes/0
Extra: 01cbae7d4c98cb93bd6da6255c7f1fe2badd3ef8494155a02a76d7afed10d1411002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e186b94a488d8aa6f2d96e9fe15d5834613185d7b9d88d66eb35d52388e3f3a 0.600000000000 1525404 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": 1055021, "vin": [ { "gen": { "height": 1055011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e186b94a488d8aa6f2d96e9fe15d5834613185d7b9d88d66eb35d52388e3f3a" } } ], "extra": [ 1, 203, 174, 125, 76, 152, 203, 147, 189, 109, 166, 37, 92, 127, 31, 226, 186, 221, 62, 248, 73, 65, 85, 160, 42, 118, 215, 175, 237, 16, 209, 65, 16, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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