Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 783d1c398d2c00f4d5e1fd428b3fc062a54c1896d1ad93dd2dce0c23235f7061

Tx prefix hash: f844313ada7f215cb15eb6f3c69bbcb59ad23d3395dc17081f3abdf525ceb93d
Tx public key: af02c954777fd8c47637e0191a8b89d93f960fcba0f527eb6843fb954232aa1a
Timestamp: 1647991838 Timestamp [UCT]: 2022-03-22 23:30:38 Age [y:d:h:m:s]: 02:357:10:30:39
Block: 464279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774771 RingCT/type: yes/0
Extra: 01af02c954777fd8c47637e0191a8b89d93f960fcba0f527eb6843fb954232aa1a021100000024d3fcec30000000000000000000

1 output(s) for total of 17.768517709000 dcy

stealth address amount amount idx
00: ae41a50af3e52bab1fd7ddec7a80294c37dc9dfaea051593a5cc6d679f9922d4 17.768517709000 882126 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": 464289, "vin": [ { "gen": { "height": 464279 } } ], "vout": [ { "amount": 17768517709, "target": { "key": "ae41a50af3e52bab1fd7ddec7a80294c37dc9dfaea051593a5cc6d679f9922d4" } } ], "extra": [ 1, 175, 2, 201, 84, 119, 127, 216, 196, 118, 55, 224, 25, 26, 139, 137, 217, 63, 150, 15, 203, 160, 245, 39, 235, 104, 67, 251, 149, 66, 50, 170, 26, 2, 17, 0, 0, 0, 36, 211, 252, 236, 48, 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