Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38505c8c6e2bd08ff1b2a030e771cf4b850980db0b3f90571a36929f90397957

Tx prefix hash: 478361e96bed979c50cefad1627ff3f9727f0782701dff5549c5530ea4e331c9
Tx public key: 23cfd0df6dcd57563f03c293c5b4086370b0b3379d198c15f1d8dbc5e63af883
Timestamp: 1722729602 Timestamp [UCT]: 2024-08-04 00:00:02 Age [y:d:h:m:s]: 00:254:02:00:19
Block: 1080185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181491 RingCT/type: yes/0
Extra: 0123cfd0df6dcd57563f03c293c5b4086370b0b3379d198c15f1d8dbc5e63af883021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1914866a9c48dff73e28f665c7e932e80abf5ec68f2373c503aa4a52adac474c 0.600000000000 1553450 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": 1080195, "vin": [ { "gen": { "height": 1080185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1914866a9c48dff73e28f665c7e932e80abf5ec68f2373c503aa4a52adac474c" } } ], "extra": [ 1, 35, 207, 208, 223, 109, 205, 87, 86, 63, 3, 194, 147, 197, 180, 8, 99, 112, 176, 179, 55, 157, 25, 140, 21, 241, 216, 219, 197, 230, 58, 248, 131, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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