Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a91c5159870861bdf1baad206e98171e0bba747375b19586d8f0d1baa542557

Tx prefix hash: 6550d1ddbcb86e5b0cfab3b221b54006f0edf5230b746693151ad4dabd4d0d26
Tx public key: 2c278fafa76783ea566988e71a2df2c9fb640d9a5fc3f4f48fde01e7290c6952
Timestamp: 1635600233 Timestamp [UCT]: 2021-10-30 13:23:53 Age [y:d:h:m:s]: 03:100:04:29:28
Block: 363657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849868 RingCT/type: yes/0
Extra: 012c278fafa76783ea566988e71a2df2c9fb640d9a5fc3f4f48fde01e7290c695202110000001006faf294000000000000000000

1 output(s) for total of 38.287217145000 dcy

stealth address amount amount idx
00: dcb9c425ca9c97fdb4adeb2f26b37201cae0105027a51066f76ab3f7c1639467 38.287217145000 739047 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": 363667, "vin": [ { "gen": { "height": 363657 } } ], "vout": [ { "amount": 38287217145, "target": { "key": "dcb9c425ca9c97fdb4adeb2f26b37201cae0105027a51066f76ab3f7c1639467" } } ], "extra": [ 1, 44, 39, 143, 175, 167, 103, 131, 234, 86, 105, 136, 231, 26, 45, 242, 201, 251, 100, 13, 154, 95, 195, 244, 244, 143, 222, 1, 231, 41, 12, 105, 82, 2, 17, 0, 0, 0, 16, 6, 250, 242, 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