Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87cada3bb6381ecf459662f1f56c24e527035c91346712b921d67712ca271f67

Tx prefix hash: 2eaa8d4dec63cd60ee3b8f9d8f1f6a7d3b79d8778e19b1ebc36f699740bbe60e
Tx public key: c00d2ee56503530b64692139723285efe62744d21e9a9e2029c0247a22ed79e9
Timestamp: 1648462013 Timestamp [UCT]: 2022-03-28 10:06:53 Age [y:d:h:m:s]: 02:317:06:15:28
Block: 468137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746057 RingCT/type: yes/0
Extra: 01c00d2ee56503530b64692139723285efe62744d21e9a9e2029c0247a22ed79e9021100000002cb8520c2000000000000000000

1 output(s) for total of 17.253135705000 dcy

stealth address amount amount idx
00: 4a44038bb901fbbdc2262e6f747bc0c3ef6709c69678c6a4a5c8f576573eb5c7 17.253135705000 886789 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": 468147, "vin": [ { "gen": { "height": 468137 } } ], "vout": [ { "amount": 17253135705, "target": { "key": "4a44038bb901fbbdc2262e6f747bc0c3ef6709c69678c6a4a5c8f576573eb5c7" } } ], "extra": [ 1, 192, 13, 46, 229, 101, 3, 83, 11, 100, 105, 33, 57, 114, 50, 133, 239, 230, 39, 68, 210, 30, 154, 158, 32, 41, 192, 36, 122, 34, 237, 121, 233, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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