Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd4020e33105b003213f7d18308c8981b26ce9defedd54d5c8910887f45a4472

Tx prefix hash: a7ac31c5d3e63e5d55e94a212bb5feddf9e65d6a0cc463419b44fca40ece561e
Tx public key: bd899da23edea4315dfb0d41030ce1957fedfd3f75946c68d2b73352be9061df
Timestamp: 1720133134 Timestamp [UCT]: 2024-07-04 22:45:34 Age [y:d:h:m:s]: 00:316:09:08:45
Block: 1058651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226097 RingCT/type: yes/0
Extra: 01bd899da23edea4315dfb0d41030ce1957fedfd3f75946c68d2b73352be9061df0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472f3c5d0d4f463557ef7d6c801a6367b7abac8410a540e0df860280c5d28a75 0.600000000000 1529108 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": 1058661, "vin": [ { "gen": { "height": 1058651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472f3c5d0d4f463557ef7d6c801a6367b7abac8410a540e0df860280c5d28a75" } } ], "extra": [ 1, 189, 137, 157, 162, 62, 222, 164, 49, 93, 251, 13, 65, 3, 12, 225, 149, 127, 237, 253, 63, 117, 148, 108, 104, 210, 183, 51, 82, 190, 144, 97, 223, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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