Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c894c294e1cc7135e4a5612b1bb48ddee3bc1fdf679be3b3a87f59f31a76f67

Tx prefix hash: a971e211b936ea2fe0d89c0704d5da53c6da4c147251209e28e2cbb8026a8ed5
Tx public key: af8cff00f27e1384003a5122e00c9615c39522c9f0bd98ea7a6063b9638e0009
Timestamp: 1711547263 Timestamp [UCT]: 2024-03-27 13:47:43 Age [y:d:h:m:s]: 01:041:03:07:17
Block: 987501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290356 RingCT/type: yes/0
Extra: 01af8cff00f27e1384003a5122e00c9615c39522c9f0bd98ea7a6063b9638e00090211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78883adede03f4c30d2bdd0fc2711b9ee3a7d3233cec993324145b3792247eb4 0.600000000000 1447752 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": 987511, "vin": [ { "gen": { "height": 987501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78883adede03f4c30d2bdd0fc2711b9ee3a7d3233cec993324145b3792247eb4" } } ], "extra": [ 1, 175, 140, 255, 0, 242, 126, 19, 132, 0, 58, 81, 34, 224, 12, 150, 21, 195, 149, 34, 201, 240, 189, 152, 234, 122, 96, 99, 185, 99, 142, 0, 9, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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