Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0963e65eda4196822c16215d22627f8dff5b93a402bff277188e4c921d3ef9da

Tx prefix hash: e9297643a85b9c6249e91c8708bd1a1b129445ac03ccd3528fa7a203681eb7cc
Tx public key: e6a554ace14ad1d336a6e5b3ac57e3479e99e63f5813ec8721fc73e4340a75f5
Timestamp: 1712985725 Timestamp [UCT]: 2024-04-13 05:22:05 Age [y:d:h:m:s]: 00:254:01:37:40
Block: 999379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181924 RingCT/type: yes/0
Extra: 01e6a554ace14ad1d336a6e5b3ac57e3479e99e63f5813ec8721fc73e4340a75f502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c2cd751bedf1922528650cd8db9fb6948d931a4fda12e1ae51ed51a09b6a827 0.600000000000 1459857 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": 999389, "vin": [ { "gen": { "height": 999379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c2cd751bedf1922528650cd8db9fb6948d931a4fda12e1ae51ed51a09b6a827" } } ], "extra": [ 1, 230, 165, 84, 172, 225, 74, 209, 211, 54, 166, 229, 179, 172, 87, 227, 71, 158, 153, 230, 63, 88, 19, 236, 135, 33, 252, 115, 228, 52, 10, 117, 245, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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