Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f0f32a2c776d22822facb0a66f93dcb3ca298327fb80f9dd61cea2905928965

Tx prefix hash: 5caaa945a61ea76cf7ab6c4040465e683340a86fcefc91003f0cd460afb91c6c
Tx public key: 287bce08100e3efcb9cfc430690200fc2cbf227e246a2aba41c197f5713e96a6
Timestamp: 1695672420 Timestamp [UCT]: 2023-09-25 20:07:00 Age [y:d:h:m:s]: 01:116:18:03:29
Block: 856066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344690 RingCT/type: yes/0
Extra: 01287bce08100e3efcb9cfc430690200fc2cbf227e246a2aba41c197f5713e96a6021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.894330454000 dcy

stealth address amount amount idx
00: 2f516e0d75a182b91bb8c83cccfb6be2f0427a70e253647ad8321332469b5124 0.894330454000 1310122 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": 856076, "vin": [ { "gen": { "height": 856066 } } ], "vout": [ { "amount": 894330454, "target": { "key": "2f516e0d75a182b91bb8c83cccfb6be2f0427a70e253647ad8321332469b5124" } } ], "extra": [ 1, 40, 123, 206, 8, 16, 14, 62, 252, 185, 207, 196, 48, 105, 2, 0, 252, 44, 191, 34, 126, 36, 106, 42, 186, 65, 193, 151, 245, 113, 62, 150, 166, 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