Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe77b60250900e9723d5c20dfdecf0bbc7a210eeef9ac7e81b957e4e8bf28f05

Tx prefix hash: b38ccf94624ebd8b521d3c00ac3dc2197736e596dc7ed000aa5a273337737950
Tx public key: bbd3422a1135fb1493f3929dbea663a8b812495ce9d1b378ab400002e316ef7a
Timestamp: 1702155402 Timestamp [UCT]: 2023-12-09 20:56:42 Age [y:d:h:m:s]: 01:038:07:44:48
Block: 909619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288742 RingCT/type: yes/0
Extra: 01bbd3422a1135fb1493f3929dbea663a8b812495ce9d1b378ab400002e316ef7a021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aaf2d3f735ac72cdf270938878704498f9df2c94f16e59054bf6c779a33b6ce 0.600000000000 1366720 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": 909629, "vin": [ { "gen": { "height": 909619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aaf2d3f735ac72cdf270938878704498f9df2c94f16e59054bf6c779a33b6ce" } } ], "extra": [ 1, 187, 211, 66, 42, 17, 53, 251, 20, 147, 243, 146, 157, 190, 166, 99, 168, 184, 18, 73, 92, 233, 209, 179, 120, 171, 64, 0, 2, 227, 22, 239, 122, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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