Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37052fd1aa98e3db0049f1e67e3772e11eafe2e8edb5b95c010bacd37115c9bc

Tx prefix hash: ffb98dec62f8494c2e4721be35421b0f21ee1a3cae343df97595529fb32b5dd6
Tx public key: 0875d1b4763c4e4ddec51e7c6d214c8ce0838f435bc610343721a9ecfa44b567
Timestamp: 1687141124 Timestamp [UCT]: 2023-06-19 02:18:44 Age [y:d:h:m:s]: 01:252:12:53:41
Block: 785387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441626 RingCT/type: yes/0
Extra: 010875d1b4763c4e4ddec51e7c6d214c8ce0838f435bc610343721a9ecfa44b567021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.533511336000 dcy

stealth address amount amount idx
00: 082c407ba17e1f92e521f8d0e3292559ddacdbba17279507ef0669ace8d99911 1.533511336000 1235344 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": 785397, "vin": [ { "gen": { "height": 785387 } } ], "vout": [ { "amount": 1533511336, "target": { "key": "082c407ba17e1f92e521f8d0e3292559ddacdbba17279507ef0669ace8d99911" } } ], "extra": [ 1, 8, 117, 209, 180, 118, 60, 78, 77, 222, 197, 30, 124, 109, 33, 76, 140, 224, 131, 143, 67, 91, 198, 16, 52, 55, 33, 169, 236, 250, 68, 181, 103, 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