Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a753a856095cd56c1d44679000a0fb23d21f1fbffccacad145cc6ec9698f20f

Tx prefix hash: e951c07f6e33e4194550aa1f73aad26902ab84d384838558f9e06fd98faafdf2
Tx public key: e22452f2d08d0577b39911df0ae436798862b3d21e7c8e9ac0184ee7723723fc
Timestamp: 1715962543 Timestamp [UCT]: 2024-05-17 16:15:43 Age [y:d:h:m:s]: 00:320:11:17:48
Block: 1024086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229044 RingCT/type: yes/0
Extra: 01e22452f2d08d0577b39911df0ae436798862b3d21e7c8e9ac0184ee7723723fc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 078aeef2aa0b657fb88ba97c4c483bc7ba92dc84ba96d9ce9c2b8095f3d7129a 0.600000000000 1489557 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": 1024096, "vin": [ { "gen": { "height": 1024086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "078aeef2aa0b657fb88ba97c4c483bc7ba92dc84ba96d9ce9c2b8095f3d7129a" } } ], "extra": [ 1, 226, 36, 82, 242, 208, 141, 5, 119, 179, 153, 17, 223, 10, 228, 54, 121, 136, 98, 179, 210, 30, 124, 142, 154, 192, 24, 78, 231, 114, 55, 35, 252, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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