Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5024e62938e40ae26d0df05e2dd65b686158f452c676c1484720f56843e6f7d7

Tx prefix hash: 61e5b8a228ca009b191ebb63488290a89a38626b89a9ed56dbbc53e2d420038d
Tx public key: 6e9db758c4c8a8f4307e621e01a3ca9717b252f2452bdddc752add9883c78bb1
Timestamp: 1658641831 Timestamp [UCT]: 2022-07-24 05:50:31 Age [y:d:h:m:s]: 02:202:19:45:57
Block: 550476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 666135 RingCT/type: yes/0
Extra: 016e9db758c4c8a8f4307e621e01a3ca9717b252f2452bdddc752add9883c78bb102110000000275e3f0e9000000000000000000

1 output(s) for total of 9.205441663000 dcy

stealth address amount amount idx
00: 47d297fce150840a4d7c7496704852840363f91e413d1f591a91bc3239202a8b 9.205441663000 981957 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": 550486, "vin": [ { "gen": { "height": 550476 } } ], "vout": [ { "amount": 9205441663, "target": { "key": "47d297fce150840a4d7c7496704852840363f91e413d1f591a91bc3239202a8b" } } ], "extra": [ 1, 110, 157, 183, 88, 196, 200, 168, 244, 48, 126, 98, 30, 1, 163, 202, 151, 23, 178, 82, 242, 69, 43, 221, 220, 117, 42, 221, 152, 131, 199, 139, 177, 2, 17, 0, 0, 0, 2, 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