Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443a47d0b00068d949ac2c4922a7fd47dce6ca7eb5874a6cf46d2d9a941a2db0

Tx prefix hash: 55fa595ab336c7aca763d7674bba11214ecb0e578a25e80f5959eb6338029b6d
Tx public key: c0b4076d849e8e0f78886470f45303d2b1e269c31d4d5f56e99f05cf47675eea
Timestamp: 1702315381 Timestamp [UCT]: 2023-12-11 17:23:01 Age [y:d:h:m:s]: 01:153:09:14:26
Block: 910945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370781 RingCT/type: yes/0
Extra: 01c0b4076d849e8e0f78886470f45303d2b1e269c31d4d5f56e99f05cf47675eea02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d64a8193186ac9d36233ea828d20b2e59169333b4e53bb524c125b202270f5 0.600000000000 1368120 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": 910955, "vin": [ { "gen": { "height": 910945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d64a8193186ac9d36233ea828d20b2e59169333b4e53bb524c125b202270f5" } } ], "extra": [ 1, 192, 180, 7, 109, 132, 158, 142, 15, 120, 136, 100, 112, 244, 83, 3, 210, 177, 226, 105, 195, 29, 77, 95, 86, 233, 159, 5, 207, 71, 103, 94, 234, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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