Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e076b451757be92036581e82ff6bd2e6da27e3bba03ff6b473cae0d254de3d96

Tx prefix hash: c4233c78a4ffdc92f596c376a89014d306e1ffd659ab6a800ed075072a024e4a
Tx public key: 65d3418da3b44011dbee078c8c3029b4a8ec8477d0a1d8253faee033f32853ad
Timestamp: 1722355253 Timestamp [UCT]: 2024-07-30 16:00:53 Age [y:d:h:m:s]: 00:176:00:51:06
Block: 1077077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125900 RingCT/type: yes/0
Extra: 0165d3418da3b44011dbee078c8c3029b4a8ec8477d0a1d8253faee033f32853ad02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849c9fea91fdfe432882ca3cc06f400346158e8fb971e12e74c64069f3fecc13 0.600000000000 1549620 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": 1077087, "vin": [ { "gen": { "height": 1077077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849c9fea91fdfe432882ca3cc06f400346158e8fb971e12e74c64069f3fecc13" } } ], "extra": [ 1, 101, 211, 65, 141, 163, 180, 64, 17, 219, 238, 7, 140, 140, 48, 41, 180, 168, 236, 132, 119, 208, 161, 216, 37, 63, 174, 224, 51, 243, 40, 83, 173, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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