Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e644aedb0da3b7a74d1eff991578d451c905f3daf6b20bc5a21f37d99d588050

Tx prefix hash: 3fe3c783fdfeece7ed5628460354acbe4a3631279ead675c0413205fa3d21301
Tx public key: fcfc4f44c0676bdfce2aeb43d3057848b734a58102f8b7cab2d41f686a0c3a13
Timestamp: 1636526056 Timestamp [UCT]: 2021-11-10 06:34:16 Age [y:d:h:m:s]: 03:167:20:25:15
Block: 371222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898352 RingCT/type: yes/0
Extra: 01fcfc4f44c0676bdfce2aeb43d3057848b734a58102f8b7cab2d41f686a0c3a130211000000021154028c000000000000000000

1 output(s) for total of 36.140601431000 dcy

stealth address amount amount idx
00: c98f12da96c28c1c13f08614f2232417c032391dc27b042e654c4911cfd6fe31 36.140601431000 752312 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": 371232, "vin": [ { "gen": { "height": 371222 } } ], "vout": [ { "amount": 36140601431, "target": { "key": "c98f12da96c28c1c13f08614f2232417c032391dc27b042e654c4911cfd6fe31" } } ], "extra": [ 1, 252, 252, 79, 68, 192, 103, 107, 223, 206, 42, 235, 67, 211, 5, 120, 72, 183, 52, 165, 129, 2, 248, 183, 202, 178, 212, 31, 104, 106, 12, 58, 19, 2, 17, 0, 0, 0, 2, 17, 84, 2, 140, 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