Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba2ceb8c1019c3ddbe9daeacd72cba87a2d5213ddb000492a00efa3f30df02ad

Tx prefix hash: 4dc3c29a6cc879128efb543809e2feb4dbdc331c2a3974385e56f287f72234c9
Tx public key: 7b03671d00b588ce3cb8ab37a7e3f662b3b9176748a945c717c51a1a5a72495d
Timestamp: 1672073321 Timestamp [UCT]: 2022-12-26 16:48:41 Age [y:d:h:m:s]: 02:110:19:46:19
Block: 661101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600886 RingCT/type: yes/0
Extra: 017b03671d00b588ce3cb8ab37a7e3f662b3b9176748a945c717c51a1a5a72495d02110000000533af99f4000000000000000000

1 output(s) for total of 3.958201702000 dcy

stealth address amount amount idx
00: 5fb63e42439b1a49e6bd0b57edb1d92eeff56ab2ae02c277eace7998c74857e9 3.958201702000 1101856 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": 661111, "vin": [ { "gen": { "height": 661101 } } ], "vout": [ { "amount": 3958201702, "target": { "key": "5fb63e42439b1a49e6bd0b57edb1d92eeff56ab2ae02c277eace7998c74857e9" } } ], "extra": [ 1, 123, 3, 103, 29, 0, 181, 136, 206, 60, 184, 171, 55, 167, 227, 246, 98, 179, 185, 23, 103, 72, 169, 69, 199, 23, 197, 26, 26, 90, 114, 73, 93, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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