Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c7a298dbb5eebc1e314d3cf03cb0be6f8c7d1225ddce4273247452880e754e

Tx prefix hash: 050f2a64396868b5cc24cf003276471a6db6f2e964b7e58a5abd0e3ea0dbd569
Tx public key: d7135f9ff6158ff9056543b2edd0a1b4b49272cdf15225594a7d440bbf73d10a
Timestamp: 1697317315 Timestamp [UCT]: 2023-10-14 21:01:55 Age [y:d:h:m:s]: 01:207:06:13:16
Block: 869710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409165 RingCT/type: yes/0
Extra: 01d7135f9ff6158ff9056543b2edd0a1b4b49272cdf15225594a7d440bbf73d10a02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.805915974000 dcy

stealth address amount amount idx
00: 00529dd8c75cbec33f7392ac8e16dbdad73d147d15d03684724fc299b4d7561f 0.805915974000 1324565 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": 869720, "vin": [ { "gen": { "height": 869710 } } ], "vout": [ { "amount": 805915974, "target": { "key": "00529dd8c75cbec33f7392ac8e16dbdad73d147d15d03684724fc299b4d7561f" } } ], "extra": [ 1, 215, 19, 95, 159, 246, 21, 143, 249, 5, 101, 67, 178, 237, 208, 161, 180, 180, 146, 114, 205, 241, 82, 37, 89, 74, 125, 68, 11, 191, 115, 209, 10, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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