Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce20440eea6d912261b1bf9fa536174886840ca33c934a15e231bba6a5480c01

Tx prefix hash: 1576bafab9ca929511a599df7cd6c14d542d3b2ee9ae45062c6a7b88b39ceb92
Tx public key: acc1c55648eb7fa4d139b4b3ffa20b49963fc7dbce7e1c2eaba57a46890404c6
Timestamp: 1673195234 Timestamp [UCT]: 2023-01-08 16:27:14 Age [y:d:h:m:s]: 02:089:02:24:32
Block: 670373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 585355 RingCT/type: yes/0
Extra: 01acc1c55648eb7fa4d139b4b3ffa20b49963fc7dbce7e1c2eaba57a46890404c602110000000571bd5189000000000000000000

1 output(s) for total of 3.687872710000 dcy

stealth address amount amount idx
00: 0d6c384789bf13214b5bbdddff7d3664f80d2fdf858a0bcdf6f9fd21ee2a2098 3.687872710000 1111774 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": 670383, "vin": [ { "gen": { "height": 670373 } } ], "vout": [ { "amount": 3687872710, "target": { "key": "0d6c384789bf13214b5bbdddff7d3664f80d2fdf858a0bcdf6f9fd21ee2a2098" } } ], "extra": [ 1, 172, 193, 197, 86, 72, 235, 127, 164, 209, 57, 180, 179, 255, 162, 11, 73, 150, 63, 199, 219, 206, 126, 28, 46, 171, 165, 122, 70, 137, 4, 4, 198, 2, 17, 0, 0, 0, 5, 113, 189, 81, 137, 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