Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae0f32dce0c8dd806010451e7cbeeee96d4fa15520ca246864b4f9200b6cb326

Tx prefix hash: fa2617f2d5854da63a462ba05cac5f90273499bc2553a8ac94e633228bfbab18
Tx public key: 0548e5e3d3ef090b12718564470e6eba88b04d9a93bd5b7d0b3dcffb66aae13d
Timestamp: 1685300005 Timestamp [UCT]: 2023-05-28 18:53:25 Age [y:d:h:m:s]: 01:280:16:51:08
Block: 770120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461812 RingCT/type: yes/0
Extra: 010548e5e3d3ef090b12718564470e6eba88b04d9a93bd5b7d0b3dcffb66aae13d021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.722950981000 dcy

stealth address amount amount idx
00: aa9913a48eebd6fcee239201cab0808300c010cc2ef27added646ae85485f2ea 1.722950981000 1219405 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": 770130, "vin": [ { "gen": { "height": 770120 } } ], "vout": [ { "amount": 1722950981, "target": { "key": "aa9913a48eebd6fcee239201cab0808300c010cc2ef27added646ae85485f2ea" } } ], "extra": [ 1, 5, 72, 229, 227, 211, 239, 9, 11, 18, 113, 133, 100, 71, 14, 110, 186, 136, 176, 77, 154, 147, 189, 91, 125, 11, 61, 207, 251, 102, 170, 225, 61, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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