Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0cbd5a3bf5117b89d603f60b39de822d1fd62eb8e44dd563a2407a48fc2f34

Tx prefix hash: 584d07018d4a8bada3b8e1edd3b29a538f1f3af78525abbb258010af5748cfae
Tx public key: ce0b8321637d9e1ac091d6e46bb9a676f54dd1375e130ecc94549e218078a67d
Timestamp: 1729600351 Timestamp [UCT]: 2024-10-22 12:32:31 Age [y:d:h:m:s]: 00:092:05:26:30
Block: 1137109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65909 RingCT/type: yes/0
Extra: 01ce0b8321637d9e1ac091d6e46bb9a676f54dd1375e130ecc94549e218078a67d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2b7877c0fdb4face95cc3cf5256d6fe7a371e3bf025340b3f308eaf32651b3 0.600000000000 1620540 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": 1137119, "vin": [ { "gen": { "height": 1137109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2b7877c0fdb4face95cc3cf5256d6fe7a371e3bf025340b3f308eaf32651b3" } } ], "extra": [ 1, 206, 11, 131, 33, 99, 125, 158, 26, 192, 145, 214, 228, 107, 185, 166, 118, 245, 77, 209, 55, 94, 19, 14, 204, 148, 84, 158, 33, 128, 120, 166, 125, 2, 17, 0, 0, 0, 5, 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