Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431dfd940761eaeaec01da4e9409df6d3ffdc8cb86c2a8ad3829de37931d2adf

Tx prefix hash: ce99105c19056576a76061eb585182315f565c31ab5fde213af9097dfa73d3aa
Tx public key: c3029479dab10f1f489e03e0df9f1a317de70448ea82386ab96c8f34e5f17a38
Timestamp: 1742066973 Timestamp [UCT]: 2025-03-15 19:29:33 Age [y:d:h:m:s]: 00:289:16:29:00
Block: 1240049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204804 RingCT/type: yes/0
Extra: 01c3029479dab10f1f489e03e0df9f1a317de70448ea82386ab96c8f34e5f17a380211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 534402fe016b5425f6a83ce62f8bd14e76f528bcdf9d9e9cb82c2c8ad652e248 0.600000000000 1727014 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": 1240059, "vin": [ { "gen": { "height": 1240049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "534402fe016b5425f6a83ce62f8bd14e76f528bcdf9d9e9cb82c2c8ad652e248" } } ], "extra": [ 1, 195, 2, 148, 121, 218, 177, 15, 31, 72, 158, 3, 224, 223, 159, 26, 49, 125, 231, 4, 72, 234, 130, 56, 106, 185, 108, 143, 52, 229, 241, 122, 56, 2, 17, 0, 0, 0, 9, 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