Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad8af4658e7cba0bea1d7b05ff364345dd2837aa3012fa3637510e31203abba8

Tx prefix hash: a375c5febed4f34c92b9deb0a3112de45cdf703fb08122b37e1418b40c87c47e
Tx public key: e3bc9566c3041e7c06d0ab39b4cd3e9b0617af82730ce6652f3cfa3a7d5d6de0
Timestamp: 1724300712 Timestamp [UCT]: 2024-08-22 04:25:12 Age [y:d:h:m:s]: 00:218:11:47:32
Block: 1093221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156003 RingCT/type: yes/0
Extra: 01e3bc9566c3041e7c06d0ab39b4cd3e9b0617af82730ce6652f3cfa3a7d5d6de002110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e9438fb29b023193812dde2a40fd2a9e43170e53cd822582816f82a135a7cf 0.600000000000 1568120 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": 1093231, "vin": [ { "gen": { "height": 1093221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e9438fb29b023193812dde2a40fd2a9e43170e53cd822582816f82a135a7cf" } } ], "extra": [ 1, 227, 188, 149, 102, 195, 4, 30, 124, 6, 208, 171, 57, 180, 205, 62, 155, 6, 23, 175, 130, 115, 12, 230, 101, 47, 60, 250, 58, 125, 93, 109, 224, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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