Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649512073a056236f3a293727f9821c5bf35dbd858574cf5fa3dd67fe59d8a9c

Tx prefix hash: ab77b14aae68c1e880c6198f286d28428c5d6a593ce7ab1678cd7fe4a8932500
Tx public key: f0f97f31061f35bf754fa8890810627a05d56e0bd030a72b0e7b14ac29b0319b
Timestamp: 1595255271 Timestamp [UCT]: 2020-07-20 14:27:51 Age [y:d:h:m:s]: 04:172:04:04:50
Block: 118614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073732 RingCT/type: yes/0
Extra: 01f0f97f31061f35bf754fa8890810627a05d56e0bd030a72b0e7b14ac29b0319b0211000003f755fb4ae5000000000000000000

1 output(s) for total of 248.303770516000 dcy

stealth address amount amount idx
00: ec7040f066321368d4b34c06ea0d772b5c9af4fac359ca89f0e29658af4c15c4 248.303770516000 202440 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": 118624, "vin": [ { "gen": { "height": 118614 } } ], "vout": [ { "amount": 248303770516, "target": { "key": "ec7040f066321368d4b34c06ea0d772b5c9af4fac359ca89f0e29658af4c15c4" } } ], "extra": [ 1, 240, 249, 127, 49, 6, 31, 53, 191, 117, 79, 168, 137, 8, 16, 98, 122, 5, 213, 110, 11, 208, 48, 167, 43, 14, 123, 20, 172, 41, 176, 49, 155, 2, 17, 0, 0, 3, 247, 85, 251, 74, 229, 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